-
Notifications
You must be signed in to change notification settings - Fork 619
[Dashboard] Replace Sentry Replay with PostHog integration #7406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Dashboard] Replace Sentry Replay with PostHog integration #7406
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## graphite-base/7406 #7406 +/- ##
===================================================
Coverage 52.06% 52.06%
===================================================
Files 945 945
Lines 63565 63565
Branches 4208 4208
===================================================
Hits 33098 33098
Misses 30361 30361
Partials 106 106
🚀 New features to boost your workflow:
|
d3b03a2 to
0ce5f79
Compare
2bd27b7 to
4e8918d
Compare
size-limit report 📦
|
Merge activity
|
### TL;DR
Replaced Sentry Replay integration with PostHog Sentry integration in the dashboard app.
### What changed?
- Removed the Sentry Replay integration that was blocking media and masking text
- Added PostHog Sentry integration with organization set to "thirdweb-dev" and projectId set to 6690186
- Updated the comment to indicate the integration of Sentry with PostHog
### How to test?
1. Verify that Sentry events are properly forwarded to PostHog
2. Check that the PostHog dashboard shows Sentry events from the thirdweb-dev organization
3. Confirm that error tracking continues to work as expected
### Why make this change?
This change integrates Sentry with PostHog to consolidate analytics and error tracking data in one platform. This will provide better correlation between user behavior and errors, improving our ability to diagnose issues and understand their impact.
<!-- start pr-codex -->
---
## PR-Codex overview
This PR focuses on integrating Sentry with PostHog in the `instrumentation-client.ts` file, replacing the previous Sentry Session Replay configuration.
### Detailed summary
- Removed the previous Sentry replay integration configuration.
- Added `posthog.sentryIntegration` with specified `organization` and `projectId`.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
4e8918d to
c09123d
Compare

TL;DR
Replaced Sentry Replay integration with PostHog Sentry integration in the dashboard app.
What changed?
How to test?
Why make this change?
This change integrates Sentry with PostHog to consolidate analytics and error tracking data in one platform. This will provide better correlation between user behavior and errors, improving our ability to diagnose issues and understand their impact.
PR-Codex overview
This PR focuses on integrating
Sentryfor error tracking and monitoring in the application, alongside existingPostHoganalytics. It involves the initialization ofSentrywith various configurations to filter errors and integrate withPostHog.Detailed summary
sentry.client.config.ts.Sentryinitialization ininstrumentation-client.tswith:allowUrlsanddenyUrlsfor filtering.dsnfor Sentry project.ignoreErrorsto ignore specific common errors.PostHogusingposthog.sentryIntegration.onRouterTransitionStartfor router navigation tracking.